fix: keep FileSynchronizer aligned with supported extensions (#286)#300
Open
officialasishkumar wants to merge 1 commit intozilliztech:masterfrom
Open
Conversation
Pass supported extensions into FileSynchronizer so the Merkle snapshot only tracks files that the indexer can actually embed. This prevents binary and other unsupported files from being hashed during sync, avoids false reindex work, and keeps the MCP and VS Code entry points aligned with core reindex behavior.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
FileSynchronizerso sync only tracks files the indexer would actually processCloses #286.
Validation
corepack pnpm exec tsc --build --forceFileSynchronizerto confirm.pdffiles are skipped while.tschanges are still detected